fonts with TeXFont
using ec-lm encoding. I found this:
(1) Any ConTeXt document produced by pdfetex 1.40.1 (even this one:
\setupoutput[pdf]
\starttext
\input tufte
\stoptext
makes my GhostScript (gs Ghostscript 8.15.3 under SuSE Linux 10.1) die
with this error:
Warning
Myriad to Type1
using fontforge, then I prepared metrics for all fonts with TeXFont
using ec-lm encoding. I found this:
(1) Any ConTeXt document produced by pdfetex 1.40.1 (even this one:
\setupoutput[pdf]
\starttext
\input tufte
\stoptext
makes my GhostScript (gs Ghostscript
Hartmut Henkel wrote:
Hi Thanh,
On Fri, 19 Jan 2007, Martin Schr�der wrote:
2007/1/18, Michal Kvasnicka [EMAIL PROTECTED]:
Excuse me this off-topic, I don't know where should I ask.
The pdftex mailing list would be a better place. See
http://www.pdftex.org/README
[...]
Good evening.
Excuse me this off-topic, I don't know where should I ask.
I've installed pdfetex 1.40.1 to be able to use hz-algorithm with
truetype fonts. Both my AdobeReader 7.x, and xpdf under SuSE Linux 10.1
view the output pdf file all right. But my gv viewer based on
ghostscript (version
2007/1/18, Michal Kvasnicka [EMAIL PROTECTED]:
Excuse me this off-topic, I don't know where should I ask.
The pdftex mailing list would be a better place. See
http://www.pdftex.org/README
[...]
Can anybody tell me what's wrong, and if there is a ghostscript version
capable to view the output
Hi Thanh,
On Fri, 19 Jan 2007, Martin Schröder wrote:
2007/1/18, Michal Kvasnicka [EMAIL PROTECTED]:
Excuse me this off-topic, I don't know where should I ask.
The pdftex mailing list would be a better place. See
http://www.pdftex.org/README
[...]
Can anybody tell me what's wrong, and
Using older ConTeXt minimals based on texexec.pl, I was able to
export TEXMFPROJECT=${PWD}/texmf
in each projects directory and use fonts local to just that project.
Switching to the latest minimal with texexec.rb, pdfetex can't find my
custom *.map files. Interestingly, it does find my custom
Stuart Jansen wrote:
Using older ConTeXt minimals based on texexec.pl, I was able to
export TEXMFPROJECT=${PWD}/texmf
in each projects directory and use fonts local to just that project.
Switching to the latest minimal with texexec.rb, pdfetex can't find my
custom *.map files
The problem of cannot open font map file is still there. I deleted
all existing context trees from my computer and downloaded the
mswincontext.zip (dt. 2006-05-17) from Pragma's website. When I run a
simple
\starttext Hello World \stoptext
file, I get
--
[1.1
Warning:
Aditya Mahajan wrote:
All these map files are located in texmf-local/fonts/map/pdftex/context/
Sounds good
TEXFONTMAPS.pdftex = .;$TEXMF/fonts/map/{pdftex,dvips,}//
TEXFONTMAPS.pdfetex = .;$TEXMF/fonts/map/{pdftex,dvips,}//
TEXFONTMAPS =
Aditya Mahajan wrote:
The problem of cannot open font map file is still there. I deleted
all existing context trees from my computer and downloaded the
mswincontext.zip (dt. 2006-05-17) from Pragma's website. When I run a
simple
\starttext Hello World \stoptext
file, I get
-local/fonts/map/dvipdfm/context/original
empty.map
but can not open it. I even tried a chmod 755 -R isoimage, but that
did not help.
How can I debug why pdfetex is not able to *open* the map files?
Aditya
--
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam
even tried a chmod 755 -R isoimage, but that
did not help.
How can I debug why pdfetex is not able to *open* the map files?
Well, there was something in the path that was interfering with
context.
set PATH=E:\Ruby\bin
E:\isoimage\usr\local\context\tex\setuptex.bat E:\isoimage\usr\local\context
--locate original-empty.map
E:/isoimage/usr/local/context/tex/texmf-local/fonts/map/dvipdfm/context/original
empty.map
but can not open it. I even tried a chmod 755 -R isoimage, but that
did not help.
How can I debug why pdfetex is not able to *open* the map files?
so, since you're
locate the files
F:\tmp\mptexmfstart --locate original-empty.map
E:/isoimage/usr/local/context/tex/texmf-local/fonts/map/dvipdfm/context/original
empty.map
but can not open it. I even tried a chmod 755 -R isoimage, but that
did not help.
How can I debug why pdfetex is not able to *open
Aditya Mahajan wrote:
Usually I get along well with cygwin. This is the first time that
cygwin has bitten me back.
i cannot test that because i don't want cygwin on my windows machine (i use gnu
bin tools compiled for windows when i need something unix) - whenevr i need
something that
On Wed, 17 May 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
Usually I get along well with cygwin. This is the first time that
cygwin has bitten me back.
i cannot test that because i don't want cygwin on my windows machine (i use
gnu bin tools compiled for windows when i need something
:
Warning: pdfetex (file lm-ec.enc): cannot open encoding file for reading
/usr/local/teTeX/share/texmf.tetex/fonts/type1/public/lm/lmr12.pfb
Warning: pdfetex (file /usr/local/teTeX/share/texmf.tetex/fonts/type1/public/lm
/lmr12.pfb): character 46 is mapped to .notdef
and a few other warnings
file says among other things:
Warning: pdfetex (file lm-ec.enc): cannot open encoding file for reading
This is the source of all the other warnings.
Cheers, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg
' installed,
myself.
The log file says among other things:
Warning: pdfetex (file lm-ec.enc): cannot open encoding file for reading
This is the source of all the other warnings.
here was a change in name of the enc files ... and there is no way to convince distributers to be that downward compatible
says among other things:
Warning: pdfetex (file lm-ec.enc): cannot open encoding file for reading
/usr/local/teTeX/share/texmf.tetex/fonts/type1/public/lm/lmr12.pfb
Warning: pdfetex (file /usr/local/teTeX/share/texmf.tetex/fonts/type1/public/lm
/lmr12.pfb): character 46 is mapped to .notdef
Hi Hans,
Thanks, as suggested by Taco and you, I downloaded cont-lmt.zip and
now everything works as expected.
Somehow I missed the change which occured this summer: sorry for
having disturbed you.
Best regards: OK
On 19 sept. 2005, at 18:00, Hans Hagen wrote:
as others already
I have compiled pdfetex 1.30 manuals ; they are at
http://www.logosrl.it
*)pdftex-a.pdf: A4
*)pdftex-l.pdf: letter
*)pdftex-s.pdf: screen
To compile, I have to patch pdftex-t.tex adding
\loadmapfile [context-base]
after
\usetypescript [adobekb] [\defaultencoding]
*)samplepdf.zip: samplepdf dir
luigi.scarso wrote:
I have compiled pdfetex 1.30 manuals ; they are at
http://www.logosrl.it
http://www.logosrl.it/context
Sorry
*)pdftex-a.pdf: A4
*)pdftex-l.pdf: letter
*)pdftex-s.pdf: screen
To compile, I have to patch pdftex-t.tex adding
\loadmapfile [context-base]
after
\usetypescript
luigi.scarso wrote:
luigi.scarso wrote:
I have compiled pdfetex 1.30 manuals ; they are at
http://www.logosrl.it
http://www.logosrl.it/context
Back to module.pdf: It is very instructive to have all module
documentation together, fresh, and very nice designed! So thank you both
Luigi
Hello again,
for those who don't know supp-vis but know what glue and penalties
are:
try \showmakeup and you get an idea where penalties, glue etc. are
inserted. This is a very cool debugging tool, because it (amazingly)
does not interfere (as far as I can see) with the actual layout.
Patrick
Hello,
this is slightly off-topic:
when using supp-vis in a plain-tex document, it runs ok with normal
TeX, but not with pdfetex:
\input supp-vis
Hello \TeX!
\bye
--
Running `PDFTeX' on `test' with ``pdftex \nonstopmode\input test.tex
Patrick Gundlach wrote:
this is slightly off-topic:
when using supp-vis in a plain-tex document, it runs ok with normal
TeX, but not with pdfetex:
% begin of supp-vis.tex
\ifx\contextversion\undefined
\let \normalunexpanded \unexpanded
\let \unexpanded \protected
\fi
\ifx\unexpanded
Hello Hans,
can you test this?
Looks fine with several different visualizations. Thanks.
Patrick
--
ConTeXt wiki: http://contextgarden.net
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
looking closer at the result of typesetting an older (Nov.
2004) document with todays pdfeTeX and context stuff I noticed that
the layout of my TOC changed:
Normally I write all setups in a SetupEnvironment file that is loaded
at the beginning of a project structure.
Like
Albrecht Kauffmann wrote:
Hi Steffen, hi all,
I've got the same problem too with TOC (and other lists). Additionally
are tables unintentionally indented when they contain local footnotes.
Could this be connected with the indentation of TOC etc.?
probably, you can test that with the patch i posted
Hi,
while looking closer at the result of typesetting an older (Nov.
2004) document with todays pdfeTeX and context stuff I noticed that
the layout of my TOC changed:
Normally I write all setups in a SetupEnvironment file that is loaded
at the beginning of a project structure.
Like
Steffen Wolfrum wrote:
Hi,
while looking closer at the result of typesetting an older (Nov. 2004)
document with todays pdfeTeX and context stuff I noticed that the layout
of my TOC changed:
Normally I write all setups in a SetupEnvironment file that is loaded at
the beginning of a project
Mojca Miklavec wrote:
The problem was most probably caused by PNG images, exported from MS
PowerPoint slides, an example is on
http://pub.mojca.org/mailinglists/context/alpha.png.
I forwarded your mail to the pdftex dev list
Hans
-
) which worked just fine until some point. After 10 minutes
pdfeTeX started crashing (and asking if the problem should be reported
to Microsoft).
If I compile the same document under MikTeX, it works just fine (except
that I can't use \setupbodyfont[phv,ss,14.4pt] command). If I compile
Matt Gushee wrote:
Warning: pdfetex (file original-public-vnr.map): \
cannot open font map file
The files exist and are world-readable, so the above must mean that
pdfetex just can't find them.
Thomas Esser has explained that pdfetex uses $TEXPSHEADERS (or maybe
$PSHEADERS) as the search
Patrick Gundlach wrote:
make sure you got your cont-sys. updated.
If by that you mean simply installing the latest version, I'm pretty
sure I did--since I ripped out all the context/ directories under
/usr/share/texmf (which is where I had always installed ConTeXt before)
and installed the
Hello Matt,
make sure you got your cont-sys. updated.
If by that you mean simply installing the latest version, I'm pretty
sure I did--since I ripped out all the context/ directories under
/usr/share/texmf (which is where I had always installed ConTeXt
before) and installed the latest
guess that's not strictly necessary, since I have
\autoloadmapfilestrue
in cont-sys.tex.
All my fonts and typescripts are in the same places they were before,
and it seems they are being found; however, pdfetex seems to be unable
to use regular TeX fonts (e.g. Computer Modern) because it can't
Hans Hagen schrieb:
Lutz Haseloff wrote:
Hi Hans, Hi all,
\loadmapfile[gbk]
\usemodule[chinese]
\usemodule[chi-simplified]
\starttext
\section{test}
\stoptext
Is this a bug in pdfetex?
welcome to the non downward compatible changes in tex and friends
you may try: texmfstart textools
Lutz Haseloff wrote:
Hi Hans, Hi all,
i tried to update pdfetex to 1.20a.
I used the standalone version by Fabrice Popineau from:
http://public.www.planetmirror.com/pub/ctan/systems/win32/fptex/standalone/
If pdfetex tries to insert a ttf-font i get an error-message:
Windows complains:
...
systems
Ed L Cashin [EMAIL PROTECTED] writes:
...
Texexec still just shows a usage message. I bet I have to change
something in texexec.ini, but I couldn't find it last time I looked.
I'll look again.
Now by doing pdfetex \cont-en test.tex I'm able to see the example
that made me want to upgrade
At 16:26 17/10/2003, you wrote:
I looked around a bit in the archives, but I'm not sure which zip that
is, so I decided to go ahead and upgrade my whole tetex to 2.0.2. I
went to pragma-ade and followed the links to find pdftex 14h.
http://www.pragma-ade.com/context/linuxtex.zip
to give you
43 matches
Mail list logo
